- Add selectDeployedChange() function for two-step selection
- Query deployed packages using LaunchQLMigrate.status()
- Query deployed changes using LaunchQLMigrate.getDeployedChanges()
- Maintain backward compatibility with existing --to string usage
- Add autocomplete prompts for package and change selection
- Update usage text with interactive examples
- Handle graceful fallback when database is unavailable

Co-Authored-By: Dan Lynch <[email protected]>

- Use target database parameter instead of default database
- Follow same pattern as deploy command with getPgEnvOptions({ database })
- Ensures interactive --to flag queries the correct target database

Co-Authored-By: Dan Lynch <[email protected]>

- Add optional preselectedPackage parameter to selectDeployedChange()
- Skip package selection when package already selected via --package or recursive mode
- Show only changes for preselected package to refine selection
- Maintain two-step selection (package then change) when no package preselected
- Improve user experience by reducing unnecessary prompts

Co-Authored-By: Dan Lynch <[email protected]>

- Update selectDeployedChange() to accept and use argv parameter
- Use 'package' and 'change' as question names to match CLI flags
- Pass argv to prompter.prompt() calls for automatic CLI argument passthrough
- Override existing package selection with scoped deployed packages when using --to
- Remove manual preselection logic in favor of inquirer's built-in handling
- Follow established pattern from deploy command and other CLI commands

Co-Authored-By: Dan Lynch <[email protected]>

- Create shared selectDeployedChange and selectDeployedPackage utilities
- Fix revert command to use scoped deployed packages when --package not supplied
- Add interactive --to flag functionality to verify command
- Both commands now use database-aware package selection with workspace fallback
- Follow established argv passthrough patterns to prevent duplicate prompts

Co-Authored-By: Dan Lynch <[email protected]>